• clockinfosMain seems like pretty dumb data structure design, but I haven't decided on a solution yet. I don't want to just tag data.rows because I don't want to persist the shown state. How do objects compare to arrays in Espruino in terms of performance?

I did some benchmarking:

var foo = [[],[],[false, false,true]];
var bar = [[true]];
var baz = {2: {2: true}}
let t = Date.now(); for (let i = 0; i < 1000; i++) { let s = foo[2][2] }; console.log(Date.now() - t);
t = Date.now(); for (let i = 0; i < 1000; i++) { let s = bar[0][0] }; console.log(Date.now() - t);
t = Date.now(); for (let i = 0; i < 1000; i++) { let s = baz[2][2] }; console.log(Date.now() - t);

foo takes 11 bytes of memory and 511 ms to complete the loop
bar and baz take 5 bytes and 496 ms to complete the loop

So objects are the winner; change incoming

The first two commits are fixing the indentation and converting to posix line endings. If you would prefer not to change these things, let me know and I can rebase without them.

Sounds good, thanks for splitting them up like that :)

Because the clockinfos are not very large, I created a second view for editing them to allow more room for swipes [...] I guess this view could have been put in the settings screen, but I did it this way for two reasons which I am not certain about and am open to feedback.

Yes - I think having it in settings would be better, as people are used to navigating to there to configure their clocks (etc), but I don't mind strongly so I'll let you decide, given you've been using the app for a while now. Another point is that the setting code loads every time the clock does, whereas if it were in settings, your clock would be faster to startup.

A few times the edit screen has shown with the wrong clockinfos. I don't know how to reproduce this, and I've made quite a few changes since the last time I saw it, so it might be fixed.

I suspect it is fixed, I can't find any problems with that kind of stuff in the code

OK, I've moved the clockinfo config to settings. There's an odd bug though.
Occasionally when tapping the back button, it acts as though I tapped on the messages widget, which is hidden.

Weird - if you edit the messages widget on your device (via the IDE), and change this code to print some logs about those dimensions it's looking at, what do you see?